Web components have become a topic of heated debate within the web development community, often sparking discussions about their future and relevance. Recently, Ryan Carniato's assertion that "Web Components Are Not the Future" was met with a counterpoint from Cory LaViska, who argued that they are indeed "the Present." Nolan Lawson, the author of the blog post, aims to bridge this divide and foster a more constructive dialogue. Lawson acknowledges Carniato's contributions to the web framework ecosystem, particularly in performance and framework design. He appreciates the insights shared in Carniato's post but believes there are some misconceptions regarding web components. He emphasizes that while performance is a critical aspect of web development, it is not the sole consideration. Other factors such as maintainability, security, usability, and accessibility also play significant roles in software development. Lawson argues that sometimes trade-offs must be made, and prioritizing performance at the expense of accessibility, for example, is not a viable approach. He draws a parallel between web performance optimization and speedrunning in video games, suggesting that while some developers may focus on micro-optimizations, the broader context of user experience and functionality should not be overlooked. Lawson believes that while minimizing DOM nodes can enhance performance, it is not always necessary to pursue the absolute fastest option. He also points out that custom elements can coexist with different frameworks, allowing for gradual migrations and the composition of micro-frontends. Addressing the concern about the "cost of standards," Lawson argues that supporting web components does not require excessive effort from framework authors. He believes that adapting to new web standards is part of the job and that developers can still create effective frameworks without being hindered by the introduction of new technologies. He acknowledges that some in the web development community may not be interested in web components, but he sees this diversity as a strength rather than a limitation. In conclusion, Lawson agrees with Carniato that web components have their limitations, particularly in areas like server-side rendering and accessibility. However, he also sees value in their use and encourages developers to explore the possibilities they offer. He emphasizes that the web is a vast landscape filled with diverse projects and approaches, and every new capability can serve as an opportunity for creativity. Ultimately, whether or not web components are the right choice depends on the specific needs and constraints of the project at hand.